🌐 Web query:

opensomeip 0.1.5 python Message class fields interface_version message_type defaults

💡 Result:

In the opensomeip 0.1.5 library, the Message class is defined as a dataclass within the opensomeip.message module [1][2]. While specific default values for the interface_version and message_type fields are not explicitly documented in the public summary, they are standard components of the SOME/IP header [3]. It is important to distinguish the library opensomeip (v0.1.5) from other Python packages such as pysomeip [4][5]. The opensomeip library is primarily a Python wrapper/interface for a C++17 implementation [6][7]. For the SOME/IP protocol generally, these fields follow the specification [3]: - interface_version: An 8-bit field representing the Major Version of the Service Interface [3]. - message_type: An 8-bit field used to differentiate message types (e.g., REQUEST, RESPONSE, ERROR) [3]. If you are programmatically inspecting the opensomeip 0.1.5 Message dataclass, you can verify the default values in your local environment using the following Python snippet: import dataclasses from opensomeip.message import Message print(dataclasses.field_defaults(Message)) If you find that the opensomeip package does not expose these fields directly in the Python dataclass constructor due to its underlying C++ architecture, you may need to interface with the RpcClient or MessageId objects provided by the library to set these headers [1][2].

Citations:

• 1: https://pypi.org/project/opensomeip/0.1.5/
• 2: https://pypi.org/project/opensomeip/
• 3: https://some-ip.com/open-someip-specification/open_someip_specification_2025-12.pdf
• 4: https://pysomeip.readthedocs.io/en/latest/someip.html
• 5: https://github.com/afflux/pysomeip/blob/master/tools/get.py
• 6: https://github.com/vtz/opensomeip
• 7: https://vtz.github.io/opensomeip/

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== repo files =="
git ls-files python/packages/jumpstarter-driver-someip | sed -n '1,120p'

echo "== conftest relevant =="
fd -a 'conftest.py' python/packages/jumpstarter-driver-someip | while read -r f; do
  rel="${f#$(pwd)/}"
  echo "--- $rel"
  wc -l "$rel"
  sed -n '440,505p' "$rel"
done

echo "== driver relevant =="
for f in python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/*.py; do
  case "$f" in
    *driver.py | *client.py | *server.py) ;;
    *) continue ;;
  esac
  echo "--- $f"
  wc -l "$f"
  rg -n "interface_version|request_id|message_type|return_code|OsipMessage\\(" "$f" -C 3 || true
done

Repository: jumpstarter-dev/jumpstarter

Length of output: 7080

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== opensomeip package version in requirements =="
rg -n "opensomeip|jumpstarter-driver-someip" python/pyproject.toml python/packages/jumpstarter-driver-someip/pyproject.toml poetry.lock uv.lock requirements*.txt -S 2>/dev/null || true

echo "== imports / constants in conftest driver and common =="
for f in python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/conftest.py \
         python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/driver.py \
         python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/common.py; do
  echo "--- $f"
  sed -n '1,80p' "$f"
done

echo "== inspect installed opensomeip if available =="
uv run python3 - <<'PY' 2>/dev/null || true
import inspect
try:
    import opensomeip
    print("opensomeip", opensomeip.__version__ if hasattr(opensomeip, "__version__") else getattr(opensomeip, "__version__", "?"))
except Exception as e:
    print("import error:", e)
    raise SystemExit

from opensomeip.message import Message, MessageId, OsipRequestId, ReturnCode, MessageType
print("Message", Message)
try:
    print("Message sig", inspect.signature(Message))
except Exception as e:
    print("Message sig error", e)
try:
    from dataclasses import fields
    for f in fields(Message):
        print("field", f.name, "default", f.default, "default_factory", f.default_factory)
except Exception as e:
    print("fields error", e)
try:
    m = Message(message_id=MessageId(0x1234, 0x5678), request_id=OsipRequestId(1, 2), payload=b"X")
    print("constructed", m)
    print("fields", {k:getattr(m,k,None) for k in ["message_id","request_id","message_type","return_code","interface_version","payload","protocol_version"]})
except Exception as e:
    print("constructed error", type(e).__name__ + ":", e)
PY

Repository: jumpstarter-dev/jumpstarter

Length of output: 7823

🌐 Web query:

vtz opensomeip 0.1.5 Message source interface_version message_type

💡 Result:

The opensomeip library (v0.1.5) provides Python bindings for the open-source C++17 implementation of the Scalable service-Oriented MiddlewarE over IP (SOME/IP) protocol [1][2]. In the context of the SOME/IP protocol, which this library implements, the fields interface_version and message_type are standard components of the SOME/IP header [3][4]: 1. Interface Version: This is an 8-bit field representing the Major Version of the service interface [3][4]. It is used to manage service definitions, detect mismatches, and allow debugging tools to identify the specific interface version in use [4]. 2. Message Type: This is an 8-bit field used to identify the type of message being transmitted [3][4]. Common values include: - 0x00: REQUEST (expects a response) [4] - 0x01: REQUEST_NO_RETURN (fire-and-forget) [4] - 0x02: NOTIFICATION (event notification) [4] - 0x80: RESPONSE (a response message) [4] - 0x81: ERROR (an error response) [4] Additionally, the third-highest bit of the Message Type (0x20) acts as a TP-Flag, which, when set, indicates that the message is a segment for the SOME/IP-TP (Transport Protocol) [3]. For specific implementation details within the opensomeip library, you should refer to the official documentation and source code hosted at the project's repository [1][2].

Citations:

• 1: https://pypi.org/project/opensomeip/0.1.5/
• 2: https://github.com/vtz/opensomeip
• 3: https://some-ip.com/open-someip-specification/open_someip_specification_2025-12.pdf
• 4: https://some-ip.com/papers/drafts/2012-07-12-SOMEIP_Specification_Draft__ReRelease.pdf

🌐 Web query:

vtz opensomeip 0.1.5 Message __init__ Python dataclass source

💡 Result:

In the opensomeip Python package (v0.1.5), the Message class is implemented as a Python dataclass within the opensomeip.message module [1][2]. As a dataclass, its structure and initialization rely on standard Python dataclass mechanics [1]. While the exact source code for the init method is automatically generated by the @dataclass decorator at runtime, the class is defined to hold SOME/IP header fields and the message payload [1]. This design is part of the project's goal to provide a "Pythonic" API that utilizes plain Python objects rather than opaque C++ wrappers for its public-facing types [1][2]. To interact with this class in your code, you can import it as follows: from opensomeip.message import Message Since it is a dataclass, you initialize it by passing the required fields directly to the constructor (e.g., Message(message_id=..., request_id=...,...)) [1]. You can verify the specific fields available by inspecting the Message class definition in the opensomeip/message.py file within the source repository [3].

Citations:

• 1: https://pypi.org/project/opensomeip/0.1.5/
• 2: https://pypi.org/project/opensomeip/
• 3: https://github.com/vtz/opensomeip

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== opensomeip source from pypi tarball, if wget is available =="
tmp="$(mktemp -d)"
cd "$tmp"
if command -v wget >/dev/null 2>&1; then
  wget -q https://files.pythonhosted.org/packages/source/o/opensomeip/opensomeip-0.1.5.tar.gz
  tar -xzf opensomeip-0.1.5.tar.gz
  if [ -f opensomeip-0.1.5/opensomeip/message.py ]; then
    sed -n '1,260p' opensomeip-0.1.5/opensomeip/message.py
  else
    echo "message.py not found"
    find opensomeip-0.1.5 -name '*.py' -maxdepth 3 | sort
  fi
else
  echo "wget unavailable"
fi

Repository: jumpstarter-dev/jumpstarter

Length of output: 246

🏁 Script executed:

#!/bin/bash
set -euo pipefail

ast-grep outline python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/driver.py \
  --items all --type function,method --match '_make_method_handler|set_method_response'

rg -n -A35 -B8 'def _make_method_handler\b|def set_method_response\b' \
  python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/driver.py

rg -n -C3 '\bopensomeip\b' \
  python/pyproject.toml \
  python/packages/jumpstarter-driver-someip/pyproject.toml \
  uv.lock 2>/dev/null || true

Length of output: 6177

🏁 Script executed:

#!/bin/bash
set -euo pipefail

make lint-fix
make pkg-test-jumpstarter-driver-someip
make pkg-ty-jumpstarter-driver-someip

Length of output: 470

🏁 Script executed:

#!/bin/bash
set -euo pipefail

sed -n '475,495p' \
  python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/conftest.py

git diff -- \
  python/packages/jumpstarter-driver-someip/jumpstarter_driver_someip/conftest.py

Length of output: 1225

driver.py

• Lines 479–496: register_event stores event-to-event-group mappings and delegates registration to the SOME/IP server; publish_event converts hexadecimal payload data to bytes and publishes by event ID.
• Lines 500–507: set_field converts hexadecimal payload data to bytes and delegates field updates to the SOME/IP server. service_id is accepted but unused.

driver_test.py

• Lines 930–971: Test fake server lifecycle and event APIs. start/stop toggle state; offer/stop_offer manage offered services; offered_services exposes service metadata; register_method, register_event, publish_event, and set_field record or store server operations.

client.py

• Lines 144–164: Client wrappers for event registration, event publication, and field updates. Payloads are hex-encoded into SomeIpPayload before invoking the corresponding RPC.